License keys are used by DeployLX to ensure the licenses have not been modified and have been created only by authorized users.
When a license file is saved, DeployLX signs the license with the license signing keys created by the Project Wizard. During the signing process the licenses are also encrypted using the same keys to prevent unauthorized users from tampering with the license.
The Project Wizard creates LSK files managed by the Key Manager and stored in[CommonApplicationData]\DeployLX\5.0\Keys.
The keys used by DeployLX must be kept secure and should be given the same care as any other essential business asset. Only trusted employees should be given access to the keys.
Caution Keys cannot be regenerated or recovered if lost. Allways back up your keys.
Public Key Encryption uses a simple algorithm applied over a series of data using one of a pair of numbers as key. The algorithm is uniquely designed such that it cannot be reversed using the same key. Instead the second of the pair is used to decrypt the data.
The first key, known as the private key, is kept secret so that no other user can encrypt the data. The public key can then be used to decrypt that data knowing that it could only have been encrypted by the complimentary private key.
By creating a signature with the private key we can ensure that a license has not been modified since it was created by the authorized user. Since each assembly is associated with only one pair of keys we can also be sure that licenses created with one key cannot be used to unlock software protected with a different set of keys.
Copy the keys used to protect your software to all machines that will generate licenses, serial numbers, activation codes or extensions from the DeployLX Manager.
To deploy keys to a license server export the keys from DeployLX and copy them to the ~/App_Data/Keys folder.
Customize the location of the key folder by setting the KeyFolder property of the license server.